050525 19:01:35  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
050525 19:01:35  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 374391983.
InnoDB: Doing recovery: scanned up to log sequence number 0 374393293
050525 19:01:35  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 0, file name 
050525 19:01:36  InnoDB: Started; log sequence number 0 374393293
050525 19:01:36  InnoDB: Starting recovery for XA transactions...
050525 19:01:36  InnoDB: 0 transactions in prepared state after recovery
050525 19:01:36 [Note] ./mysqld: ready for connections.
Version: '5.0.4-beta-debug-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Debug (GPL)
050525 19:01:36 [ERROR] ./mysqld: Table './mysql/proc' is marked as crashed and should be repaired
050525 19:01:36 [ERROR] ./mysqld: Table './mysql/proc' is marked as crashed and should be repaired
050525 19:01:36 [ERROR] ./mysqld: Table './mysql/proc' is marked as crashed and should be repaired
pure virtual method called
mysqld got signal 6;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=16777216
read_buffer_size=258048
max_used_connections=37
max_connections=100
threads_connected=36
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8ca4798
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbfd3ebb8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a2cb3
0x838d688
0x8398d61
0x838da19
0x8399180
0x83fd9c8
0x83fd9ed
0x83fd6fb
0x804d747
0x80b2d86
0x8425f55
0x81a44be
0x81a43d2
0x80ba366
0x80bbfba
0x80b3b34
0x80b33fc
0x80b26b4
0x838ae3c
0x83b499a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8d93438 = Create trigger trg_3_404001 before INSERT on t100 for each row set new.f2=1000
thd->thread_id=10
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
